home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 1
/
Cream of the Crop 1.iso
/
UTILITY
/
VMIDRV11.ARJ
/
README.1ST
< prev
next >
Wrap
Text File
|
1991-09-10
|
73KB
|
3,326 lines
Vermont Microsystems
Windows 3.0 Driver
Installation Notes
VERSION 1.10
TABLE OF CONTENTS
1... INSTALLATION PROCEDURE
2... KNOWN PROBLEMS
3... NOTES
4... IF YOU HAVE PROBLEMS...
5... TECH NOTES
6... BUGS FIXED FROM VERSION 1.00
7... REPORTED BUGS
INSTALLATION PROCEDURE
1. If you have not already done so, install the Vermont
Microsystems graphics processor in you system as per the installation
Guide. Be sure to run INSTALLV to ensure that the DOS driver and
firmware is properly loaded.
2. If you have previously installed an earlier version of the
Windows driver, SETUP will not copy the new driver files over
This is a bug in the Microsoft SETUP. To insure proper operation
delete the file VMI.DRV from the \WINDOWS\SYSTEM directory.
3. Run Windows SETUP either from the Windows 3.0 distribution
diskettes or the WINDOWS directory if you have previously
installed WINDOWS 3.0. Do not run SETUP from Windows. The option
to install a third party ('Other') driver will not appear.
4. Under the 'SYSTEM INFORMATION' Menu, select the DISPLAY option.
5. In response to the 'SELECT DISPLAY from the following list' prompt,
select 'Other'. This should ask you for the diskette supplied by
Vermont Microsystems containing the Windows 3.0 driver.
6. The Windows 3.0 driver files are contained in a subdirectory on
the disk called \WIN3. When prompted as to where to find the disk
and requested files, make the response box look like
(assuming diskette in A: drive):
A:\WIN3
7. In response to the 'SELECT DISPLAY from the following list' prompt
select:
Vermont Microsystems Graphics Processor
8. Follow the rest of the Windows SETUP procedure normally.
12. The Vermont Microsystems Graphics Processor driver is now fully
installed in the Windows 3.0 environment.
KNOWN PROBLEMS
1. Older, incompatible version of the Novell Network have cause
intermitant hangs. If the Windows Setup procedure did not like
your network configuration and you are running in a network
environment you may run into problems.
2. Older versions of QEMM.SYS in your CONFIG.SYS at setup time can
cause problems while running SETUP. Save your current CONFIG.SYS,
delete the QEMM.SYS line from you CONFIG.SYS and rerun SETUP.
NOTES
The Windows 3.0 default color scheme results in a dithered
Active Window Title Bar for 4-bit boards. This results in a
small performance degradation. The color scheme can be modified
via the Control Panel.
IF YOU HAVE PROBLEMS...
Common errors for Windows installation are:
1. CONFIG.SYS line not modified as per step 2 in the Installation
Procedure above.
2. Older versions of QEMM.SYS in your CONFIG.SYS at setup time can
cause problems while running SETUP. Save your current CONFIG.SYS,
delete the QEMM.SYS line from you CONFIG.SYS and rerun SETUP.
3. Most Windows problems are Windows environment problems. We
strongly recommend using the Microsoft supplied MOUSE.SYS,
HIMEM.SYS and SMARTDRV.SYS. These drivers control the mouse,
manage extended memory and cache disk requests respectively.
Using other drivers to perform the same functions can cause
problems.
4. Many Windows 2.0 applications will run under Windows 3.0. In
the Windows 3.0 environment they generate an error message but
the option exists to ignore the error message. While the
application may appear to run correctly corruption of the
environment may be taking place. Take these error messages
seriously. Update the application or use sparingly.
5. Before calling technical support with a problem, look
through the TECH NOTES section and the KNOWN BUGS section.
Your problem may be addressed there.
TECH NOTES
Tech Note
Windows 3.0 Native Driver
Title: Divide error when trying to start Windows
Date: 26-Mar-91
By: evh
When invoking Windows it may fail to switch into high res mode and simply
return to DOS, giving a divide error. The reason Windows fails is
for one of two reasons:
1) The driver was unable to open the DOS driver
2) The driver was unable to create the on-board buffer
the Windows driver uses.
The reason the divide error is reported is apparently a bug in
Windows. The function which opens the driver is supposed to return
a structure length upon success and zero upon failure. It looks like even
when zero is returned Windows tries to perform some arithmetic
operation using the 'structure length'.
Tech Note
Windows 3.0
Title: Setup hangs when run from DOS
Date: 18-April-91
By: evh
The Microsoft Windows Setup program can be run in one of three ways.
First, it can be run from inside of Windows. When invoked this way
the 'other' option for display drivers is not available, so our
driver cannot be installed in this way.
Setup can also be run directly from the Windows distribution disks.
The only disadvantage to this is that if Windows has already been
installed, it must be completely reinstalled. This is very
time consuming.
The preferred way of installing the VMI driver when Windows has
already been installed is to invoked Setup from DOS. Unfortunately,
there is a known bug in Setup which causes it to hang occasionally
when invoked in this manner. If this happens, the only option is to
install Windows from the distribution disks.
Tech Note
Windows 3.0
Title: Different installations for 5 1/4" and 3 1/2" format disks
Date: 18-April-91
By: evh
The Windows Setup program uses a script file called setup.inf.
Likewise the VMI driver disks contain a companion script file called
oemsetup.inf. These files contain commands for the Windows
installation, including such things as what disks contain which
files. Because there are a different number of disks for Windows
depending on whether it came on 5 1/4" floppies or 3 1/2" floppies,
the setup.inf files are different. Therefore, you must be very
careful about mixing and matching Windows and VMI format floppies.
The indication of this problem will be that Windows will ask the user
to insert a particular disk, then give a "file not found" error.
Because of this problem, VMI ships the oemsetup.inf files for both
formats. They will be named oemsetup.514 for the 5 1/4" floppy
format, and oemsetup.350 for the 3 1/2" floppy format. There will
also be a file names oemsetup.inf. This will be the file for the
floppy format on which the driver resides. If you need switch to the
other format, simply copy the appropriate oemsetup file over the one
named oemsetup.inf.
Tech Note
Windows 3.0
Title: Switching between CV and Microsoft Windows
Date: 18-April-91
By: evh
This tech note was copied from a technical bulletin written by:
4D Graphics ESS
1800 NE 44th Street
Suite 210
Renton, WA 98056
It is included here as a service to VMI customers. The validity of
the information cannot be verified by VMI. If you have any questions
please contact 4D Graphics ESS.
*************************************************************
Microsoft has created their own 386 specification, "DOS Protected
Memory Interface" (DPMI), which is not compatible with "Virtual
Control Program Interface" (VCPI), required by Personal Designer.
DPMI is part of the HIMEM.SYS device driver installed by the Windows
installation program. If HIMEM.SYS is installed on your system,
Personal Designer will not run. Instead it produces a somewhat
cryptic error message such as "Cannot lock stack page frame." Until
recently the best way to get around the problem has been to maintain
two different CONFIG.SYS files, and re-boot your system with each
configuration.
Recently QuarterDeck (213-392-9701) has released a new version of
their QEMM memory manager (version 5.11) which can provide VCPI
memory for the Personal Designer and other programs, and DPMI memory
for Windows at the same time.
Qualitas Software (301-907-6700) has also released version 5.10 of
their 386MAX and BLUEMAX (for PS/2's) memory managers with similar
capabilites.
Even with these utilities Personal Designer cannot run while Windows
is running in 386 Enhanced Mode. However, running either of the
products named above instead of HIMEM.SYS, GCD can at least be run
from inside of Windows real mode, Windows standard mode, or from DOS.
Due to potential conflicts between device drivers, it is best to run
Personal Designer from inside of Windows using either dual screens
(say a VGA for Windows and a high performance card for Personal
Designer), or sharing a simple device such as VGA or EGA.
*************************************************************
Tech Note
Windows 3.0
Title: Fonts that do display properly with the VMI Cobra Driver
Date: 19-April-91
By: evh
This problem showed up when we switched from a VGA driver to the
Cobra driver. The ZapfDingbats font characters did not display.
Everything printed properly, but the characters were displayed in
Courier.
Windows has two types of fonts (stored in files with the extent
'.FON'). Some fonts are scaleable and can be used with displays of
any resolution. In the win.ini file they are specified by 'All res',
as in:
Modern (All res)=MODERN.FON
Other fonts are resolution specific. They are specified by the
device that most closely matches the font, as in:
Helv 8,10,12,14,18,24 (8514/a res)=HELVF.FON
or:
Courier 10,12,15 (VGA res)=COURE.FON
Some fonts are provided with Windows, but others must be obtained
elsewhere. If the font is, for example, a Postscript font that
displays on a VGA but not the Cobra Elite or Cobra Plus, the problem
is that the screen font which corresponds to the Postscript font must
be loaded. VMI's Cobra boards are set up to use fonts at the 8514/a
resolution.
One source for screen fonts is Pacific Page which makes the
Postscript add-on cartridges for HP laser printers.
Tech Note
Windows 3.0
Title: DOS box won't work in 386 enhanced mode
Date: 24-April-91
By: evh
On older machines the default vga Virtual Device Driver (VDD) and 386
grabber don't always work. The symptom is that when attempting to
run the DOS box - in either full screen or windowed mode - Windows
reports that the version of 386 Windows is out of synch and that 386
Windows should be reinstalled.
The way our driver is installed, we use the default Windows vga
grabbers and VDD. The default Windows VDD is actually in the Windows
kernel. You can tell this because in the system.ini file the name of
the VDD is *vddvga. The '*' means that 'vddvga' is in the kernel.
All the other VDD's are separate files with a file extent of '.386.'
Starting in version 1.00 of the Cobra Elite driver, and in all
versions of the Cobra Plus driver, the 386 grabber and the VDD are
included. However, in version 0.95 of the Cobra Elite driver this
problem may show up.
Tech Note
Windows 3.0
Title: Using The Bitstream Facelift
Date: 1-May-91
By: evh
The current version of the Bitsream Facelift (Bitstram fonts) will
not work with the Cobra Elite/Plus Windows 3.0 driver. Here is what
we know about why it doesn't work:
When the Windows driver is invoked, the following happens:
1) A function called Inquire gets called. It doesn't really do
anything.
2) A function called Enable gets called twice. The first time it is
called, the driver is supposed to return information about itself in
a structure called the GDIINFO structure. The caller passes a pointer
to a data area into which the GDIINFO structure is to be copied.
Enable returns in the AX register the size of the GDIINFO structure.
If there is an error, Enable returns 0.
3) The second time Enable gets called, the hardware gets physically
enabled. This is where we - normally - switch into high resolution
mode.
What is happening with the Bitstream Facelift is that the first time
Enable gets called, we do exactly what we are supposed to and
everything looks great from our standpoint. The DOS driver is opened
successfully, we create our off-screen memory buffer, we copy the
GDIINFO structure and return its size - which happens to be 6E hex -
in the AX register. Great. Wonderful.
Unfortunately, however, the Bitstream shell apparently doesn't like
what we are returning in the GDIINFO structure because it continues
to call Enable asking not to physically enable the hardware, but to
return the GDIINFO structure. When running without a debugger, this
puts you into an endless loop. When running with a debugger, it
eventually gives up and lets you quit.
As far as I can tell, we are doing everything perfectly legally and
according to the spec, so I don't know of anything I can do to make
this work. We have contacted Bitstream and are awaiting a reply.
Tech Note
Windows 3.0
Title: Non-Windows applications that won't work in the DOS box
Date: 6-May-91
By: evh
Not all non-Windows applications will work in the DOS box. In
Windows terms, they must be 'well-behaved.' Microsoft provides
developers with a list of the things that must be done to make their
non-Windows applications well-behaved.
For example, applications cannot write directly to screen memory.
They must use interrupt 10 to write to the screen. Microsoft
provides a way for applications to detect if the are running under
Windows so they can modify the way they deal with screen memory.
Non-Windows applications must also properly save and restore
interrupt vectors. In general, changing interrupt vectors will get
you into a lot of trouble when running under Windows.
The utility program XTNET is a known application that is not
well-behaved. There are sure to be others.
Tech Note
Windows 3.0
Title: Problems with Windows Setup and Virtual Display Driver
Date: 20-May-91
By: evh
Starting with version 1.00 of the Cobra Elite/Cobra Plus driver, VMI
is shipping its own Virtual Device Driver (VDD) and 386 grabber.
This solves a problem some people were having running the DOS box,
especially on older machines. Unfortunately this also uncoveres a
bug in the Windows Setup program. This bug only occurs when doing a
full install from the Windows distribution disks. It does not happen
when running Setup in maintenance mode.
When installing a third-party VDD, Setup correctly copies the VDD
from the oem disk. Unfortunately, it also prompts for the VDD later
in the install cycle when Windows is installing files from disk #4
(on the 5 1/4" disks) which is where Microsoft's VDD's are. Usually
Setup displays a dialog box with the message:
Please insert the following disk:
followed by the name of the disk. This is followed by an edit box
with the name of the disk driver and sub-directory where the file can
be found, i.e.:
a:
When there is a third-party VDD, the name of the disk and the edit
box are both blank. If you happen to know enough to put the oem disk
back in the driver and enter the correct driver letter and
sub-directory, Setup will continue and run fine. Users should put
the VMI disk in the driver and enter:
a:\win3
in the edit box (when installing from driver a:).
Microsoft is aware of the problem. There is a tech note on their
bulletin board. It is not clear whether they plan to fix it.
Tech Note
Windows 3.0
Title: Windows Setup puts ega.sys in config.sys
Date: 24-May-91
By: evh
There is a but in the Microsoft Windows Setup program which puts the
following line in your config.sys file:
device=ega.sys
This line should be deleted. the ega.sys file is not copied onto
your disk unless you install the ega display driver.
Tech Note
Windows 3.0
Title: Dingbats
Date: 30-Aug-91
By: Eric Van Horn
There are at least two known problems having to do with the Dingbats
font. The problems apparently stem from the fact that Microsoft does
not ship a Dingbats font which works with drivers which use screen
metrics other than those for a VGA. Since the VMI drivers use 8514
font metrics, this causes several problems.
The first problem is that in Microsoft Word, the text will not be
displayed properly if Dingbats is selected. This will be true, in
fact, of any application which uses Dingbats. The solution is to
purchase a Dingbats font.
The second problem is more serious. Some applications apparently do
not handle the case where a font is not available. One of these is
PowerPoint. PowerPoint may crash if Dingbats is selected. The
solution here is the same... purchase a Dingbats font and install it.
Everything will then work fine.
Tech Note
Windows 3.0
Title: Trashed Box Borders
Date: September 6, 1991
By: Richard H.
As first seen in the X/Series driver running PowerPoint, the
borders around various boxes may occasionally have their lower
right edges erased. This has been observed in the PowerPoint
"define styles..." dialog box, whereby the static text box
that shows a sample of the newly selected style will be blitzed.
This does not appear to be a bug in our driver, but rather a
problem with the Windows GDI. When it draws the box border, it
requests a bordered rectangle of dimensions <a,b,c,d> (in <left,
top, right,bottom> notation). As per DDK spec, this should
result in a border of <a,b,c-1,d-1>. When it subsequently clears
the rectangle prior to drawing the new style sample, it requests
an unbordered, interior-filled rectangle of <a+1,b+1,c,d>. This
will result in clearing the area <a+1,b+1,c-1,d-1>, which
happens to include the lower right edges of the text box.
The VGA driver does not manifest this problem, but this is due to
the fact that it doesn't support rectangular polygonal drawing.
Hence the GDI uses different driver calls to accomplish its
purpose. When we change our driver to indicate that we don't
support rectangles, the problem goes away.
Our plan is to continue to support the rectangle primitive
because of the performance boost it presumbly supplies.
Hopefully the GDI problem is localized. If necessary, we can
reverse this decision later, or supply a special version of the
driver where warranted. We should reinvestigate when Windows 3.1
becomes available.
FIXED BUGS
Software Anomaly Report
Windows 3.0 Driver
Date: 5-June-91
Reported By: Bruce Gilbert
Driver: X/Series
Found in Version: 0.92
Priority (1,2 or 3): 1
Problem:
The Pantone color selection module in Pagemaker 4.0 will crash 4 out
of 5 times.
Fixed By: evh
Date: 11-June-91
Fixed after version: 1.00
Fix:
This was already fixed, apparently when we fixed the palette problems
in the Elite.
Modules affected:
None.
Software Anomaly Report
Windows 3.0 Driver
Date: 24-May-91
Reported By: evh
Found in Version: 0.98
Priority (1,2 or 3): 1
Problem:
Cobra Plus driver hangs on startup.
Fixed By: evh
Date: 30-May-91
Fixed after version: 1.00
Fix:
The sprint needed to be disabled.
Modules affected:
ENDevice.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 11-June-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 1
Problem:
The highliting and screen redrawing is screwed up in the dialog box
to select a window in the Program Manager. To duplicate this bug:
1. Select the "Window" menu item in the Program Manager.
2. Select "More Windows" from the menu.
3. Scroll the window
Fixed By: evh
Date: 11-June-91
Fixed after version: 1.00
Fix:
In special_blit the ah register was being cleared but we really
needed the ax register cleared. As a result, the linfun wasn't
always being set properly.
Modules affected:
special.blt
Software Anomaly Report
Windows 3.0 Driver
Date: 11-June-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem:
When entering text in NotePad, the line is in reverse video from the
cursor to the end of the line.
Fixed By: evh
Date: 11-June-91
Fixed after version: 1.00
Fix:
Apparently fixed in special.blt when fixing either special_rect or
special_blit.
Modules affected:
special.blt
Software Anomaly Report
Windows 3.0 Driver
Date: 11-June-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem:
When the Program Manager window is maximized or minimized, the
windows inside aren't redrawn.
Fixed By: evh
Date: 11-June-91
Fixed after version: 1.00
Fix:
Already fixed in special.blt.
Modules affected:
special.blt
Software Anomaly Report
Windows 3.0 Driver
Date: 11-June-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem:
When drawing a rectangle in Paint, the cursor leaves a trail behind
it.
Fixed By: MJB
Date: 12-June-91
Fixed after version:
Fix: Added cursor exclusion code to polyline code.
Modules affected: polydev.asm , polyline.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 11-June-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem:
The menu items aren't completely drawn. To reproduce:
1. Start Corel Draw
2. Pull down the main menu. The items will be incomplete.
Fixed By: evh
Date: 14-June-91
Fixed after version: 1.00
Fix:
The setup_bitmap macro tested the line pattern flag, but called
_vmlinfun instead of _vmlinpat
Modules affected:
vm_map.inc
Software Anomaly Report
Windows 3.0 Driver
Date: 5/23/91
Reported By: Jeff Sweeny
Driver: Cobra
Found in Version: .98
Priority (1,2 or 3): 3 - BMP files don't display properly.
Problem: Follow these steps...Select control panel...Desktop...change
the wallpaper pattern. If you select a BMP file that is a scanned in
photograph it will be displayed but the pallette is all screwed up.
Exit windows 3.0 then go back in and the colors look fine.
Fixed By: evh
Date: 17-June-91
Fixed after version: 1.00
Fix:
As far as I can tell, this is a bug in the Program Manager. When
palette management is enabled, the Program Manager assumes that the
current palette is always the default Windows palette. When a
background bitmap that has its own palette is used, the background
bitmap loads its own palette. When the Program Manager then starts
up an application that changes the palette, it assumes that the
current palette is the default Windows palette. This has two
affects. One is that if any colors on the screen are updated, they
will be updated incorectly. The other is that when you quit the app,
the default palette will be restored instead of the original one.
Modules affected:
None.
Software Anomaly Report
Windows 3.0 Driver
Date: 14-June-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem:
The color palette in CorelDraw does not display properly the first
time it comes up.
Fixed By: evh
Date: 17-June-91
Fixed after version: 1.00
Fix:
As far as I can tell, this is a bug in the Program Manager. When
palette management is enabled, the Program Manager assumes that the
current palette is always the default Windows palette. When a
background bitmap that has its own palette is used, the background
bitmap loads its own palette. When the Program Manager then starts
up an application that changes the palette, it assumes that the
current palette is the default Windows palette. This has two
affects. One is that if any colors on the screen are updated, they
will be updated incorectly. The other is that when you quit the app,
the default palette will be restored instead of the original one.
Modules affected:
None.
Software Anomaly Report
Windows 3.0 Driver
Date: 6/11/91
Reported By: MJB
Driver: XSERIES
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem: Paint Roller in paint doesn't work.
Fixed By: MJB
Date: week of 6/10 - 6/14
Fixed after version: 1.00
Fix: Scanline drawing was ifdef PGL'd out!
Modules affected: Scanline.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 6/16/91
Reported By: MJB
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem: Paint roller filling in black over a gray scale brush (dotted)
doesn't cut it.
Fixed By: MJB
Date: 6/16/91
Fixed after version: 1.00
Fix: Fixed drawbrush function in scandev. Looped to wrong place: si not
being incremented so only first scanline drawn (over and over). ON
XSERIES ONLY.
Modules affected: scandev.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 6/16/91
Reported By: MJB
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 1
Problem: Cursor not properly excluded when windows brought up with tiled
Ribbon bmp.
Fixed By: MJB
Date: 6/16/91
Fixed after version: 1.00
Fix: SetCursor init'ed variables real_x and real_y, adjusting for hot spots.
The variables x_cell, y_cell set in move cursor were not updated. Differed
by hot spot sizes.
Modules affected: Cursors.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 13-June-91
Reported By: evh
Driver: Cobra Plus
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem:
In Paint, bitmapped graphics do not display consistently and often
have lines and other spots after panning.
Fixed By: MJB
Date: 6/17/91
Fixed after version: 1.00
Fix: Fixed drawbrush function in scandev. Looped to wrong place: si not
being incremented so only first scanline drawn (over and over). ON
XSERIES ONLY.
Modules affected: scandev.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 13-June-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem:
Inserting text in Word does not work properly. To recreate:
1) Move the insertion bar to the center of a line of text.
2) Insert a character.
(Opaque rectangle bug?)
Fixed By: MJB
Date: 6/17/91
Fixed after version: 1.00
Fix: Added cursor exclusion to strblt.
Modules affected: strblt.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 6/16/91
Reported By: MJB
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem: In paint, inserting text in the middle of text string is screwy.
Zooming in, out, repainting screen doesn't correct it.
Fixed By: NOT FIXED. Same thing happens on the VGA. Either it is not
a bug or it is Windows' bug.
Date: 6/20/91
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 7/01/91
Reported By: MJB
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem: Winbench full arcs: scanlines not long enough to erase polyline.
Maybe windows bug. Spec says exclude last pt for scanlines.
Fixed By: Punted by MJB
Date: 7/1/91
Fixed after version:
Fix: VGA does same thing: I will assume bug in Benchmark app.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 6/13/91
Reported By: MJB
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem: Scanlines displaying in wrong color in Paintbrush (paint roller).
Fixed By:
Date: 7/01/91
Fixed after version: 1.00
Fix: BeginScantoDevice assumed solid brushes were actually solid. The
dithered solid was not supported. Now it is. The accel field of
oem_brush is tested against both BS_SOLID and SOLID_BRUSH now.
Alternating patterns (2 colors) are done with linepatterns in
opaque mode.
Modules affected: Scandev.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 13-June-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem:
The DOS box does not work when the system has a mono card but no VGA
on a Gateway 486. It is not clear if this is also a problem on other
platforms.
Fixed By: evh
Date: 30-July-91
Fixed after version: 1.00 alpha
Fix:
Need to install mon grabbers and VDD.
Modules affected:
None.
Software Anomaly Report
Windows 3.0 Driver
Date: june 17th 1991
Reported By: jim carroll
Driver: cobra plus/ elite using a plus.
Found in Version: ? installation disk v. 1.13
Priority (1,2 or 3):
Problem:
When going to the dos box, it will not let me get a enhanced window.
instead, because I don't have a VGA, it brings me to monocrome. When I
try to exit back to windows, there is a pause, the windows program manager is
re-painted, and then I am kicked back out to dos on the monocrome. I can't
tell if I am kicked back out to the shell, or out to the primary.
Fixed By: evh
Date: 30-July-91
Fixed after version: 1.00 alpha
Fix:
Needs monochrome grabbers
Modules affected:
None
Software Anomaly Report
Windows 3.0 Driver
Date: 29-July-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 2
Problem:
Some of the blits don't go all the way to the bottom of the screen.
It looks like they are missing the bottom scanline or two.
Fixed By: evh
Date: 30-July-1991
Fixed after version: 1.00 alpha
Fix:
The clipping rectangle was being improperly restored.
Modules affected:
SBStrDraw.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 7/15/91
Reported By: Paul Angstman
Driver: Windows 3.0
Found in Version: Whatever's on the Net as of 7/15
Priority (1,2 or 3): I don't know
Problem: In Microsoft word, highlight a paragraph, then justify it. Then
hightlight a word in that paragraph and change it to another
character. You'll see little bits of RC within that line of text.
If you do this with left or right justification, the text is okey
dokey.
Fixed By: evh
Date: 30-July-1991
Fixed after version: 1.00 alpha
Fix:
When drawing text with a width vector, we were doing a move after
drawing each character. When the text was being drawn opaquely, the
spaces in between the characters weren't being blanked out. Now the
opaque rectangle is not minimized so it is drawn before the string is
drawn.
Modules affected:
SBRectSet.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 29-July-19
Reported By: evh
Driver: X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 2
Problem:
When typing in Word, there is RC.
Fixed By: evh
Date: 31-July-91
Fixed after version: 1.00 alpha
Fix:
Couldn't reproduce. Probably fixed elsewhere.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 11-June-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 1
Problem:
fwload won't work with VGA pass-through hooked up on a 486 machine.
Fixed By: evh
Date: 31-July-91
Fixed after version: 1.00 alpha
Fix:
This was a hardware problem with the X/Series.
Modules affected:
None.
Software Anomaly Report
Windows 3.0 Driver
Date: 05/31/91
Reported By: jlk
Driver: Cobra
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem: Reformatted, several paragraphs from left alignment to
justified. Resulting screen contained residual crud. PgUp/PgDn did
not fully clear up problem. Showing background color through proportional
spacing in between words.
Fixed By: evh
Date: 31-July-91
Fixed after version: 1.00 alpha
Fix:
This was probably the same problem as the text with width vectors not
clearing the space in between characters. It appears to work fine
now.
Modules affected:
SBRectSet.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 05/31/91
Reported By: jlk
Driver: Cobra
Found in Version: 1.00
Priority (1,2 or 3): 2 (I'm a middle of the road kinda guy)
Problem: Running Word for Windows. I had entered some text,
highlited two characters and went into Format Character. Text was 14
point schoolbook, I selected 8point superscript up 6points. When I
returned, the area around the supersripted text had residual crud.
PgUp/PgDn cleaned up the display.
Running on Spetrum at 1024 res.
Fixed By: evh
Date: 31-July-91
Fixed after version: 1.00 alpha
Fix:
In the routine SBStrDraw we check to see if there is an opaque
rectangle to the left of the string. If there is, we draw it before
the string is drawn, and otherwise we let the PGL opaque draw
routine do the opaqueing. This doesn't work, however, for
superscript and subscript text, because the opaque rectangle also
needs to opaque any area above and/or below the string. I put in two
additional checks, so that if there is opaque data above or below the
string, we will draw the opaque rectangle.
Modules affected:
SBStrDraw.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 5/22/91
Reported By: Paul Angstman
Driver: Cobra (not X/Series -mjb)
Found in Version: .98
Priority (1,2 or 3): 3
Problem: In Paintbrush -- select text; put in several characters; change the
size of the text to something 64 or larger. The previously typed
text is clipped on the bottom, but new text entered is okey dokey.
Fixed By: evh
Date: 31-July-91
Fixed after version: 1.00 alpha
Fix:
Couldn't reproduce. Apparently this was fixed along the way.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 14-June-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem:
The color palette in CorelDraw does not display properly the first
time it comes up.
Fixed By: evh
Date: 31-July-91
Fixed after version: 1.00 alpha
Fix:
Couldn't reproduce. Apparently fixed along the way.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 6/24/91
Reported By: MBS
Driver: Cobra Elite
Found in Version: 0.95
Priority (1,2 or 3): 2
Problem: Color palette in Corel Draw is incorrect with Cobra Elite
(i.e. 16 color card).
Fixed By: evh
Date: 31-July-91
Fixed after version: 1.00 alpha
Fix:
Couldn't reproduce. Apparently this was fixed along the way.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 5-June-91
Reported By: Bruce Gilbert
Driver: X/Series
Found in Version: 0.92
Priority (1,2 or 3): 1
Problem:
Driver does not work with DOS 5.0, apparently due to EMM386.exe.
Fixed By: evh
Date: 31-July-91
Fixed after version: 1.00 alpha
Fix:
If it did not work before, it does now.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 31-July-91
Reported By: evh
Driver: X/Series 16 color
Found in Version: 1.00 alpha
Priority (1,2 or 3): 2
Problem:
Grayed text in menu items does not invert properly when that menu
item is selected.
Fixed By: evh
Date: 1-Aug-91
Fixed after version: 1.00 alpha
Fix:
The mono bits weren't being set in rgb_to_ipc().
Modules affected:
rgb2ipc.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 1-Aug-91
Reported By: evh
Driver: 16 color X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 1
Problem:
Minimizing and then maximizing a window on the desktop crashes the
system. This only happens on the 16 color cards.
Fixed By: evh
Date: 2-Aug-91
Fixed after version: 1.00 alpha
Fix:
The color tables for 16 color mode were in the code segment, so in
protected mode they crashed. I moved them to the data segment.
Modules affected:
bmc_ite.asm
bmc_eti.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 6/13/91
Reported By: MJB
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 3
Problem: Solid scanlines are being drawn with vmblkwr instead of vmvector
if Greyscale. Sometimes uses patterned brush for solid black. Slow.
Fixed By: MJB
Date: 8/2/91
Fixed after version:
Fix: Not sure, but I know it's ok now.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 31-July-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 1
Problem:
SaveScreenBitmap does not work reliably.
Fixed By: evh
Date: 13-Aug-91
Fixed after version: 1.00 alpha
Fix:
The buffer size not being determined properly.
Modules affected:
ENDevice.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 6/21/91
Reported By: MJB
Driver: X/SERIES
Found in Version: 1.00
Priority (1,2 or 3): 3
Problem: Background text test in winbench: when cursor is excluded, leaves a
thick horiz line as if clipped when turned off.
Fixed By: Tested by MJB
Date: 8/14/91
Fixed after version:
Fix: Do not know, but it doesn't happen now.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: July 1, 1991
Reported By: MJB
Driver: X/Series
Found in Version: after 1.00
Priority (1,2 or 3): 1
Problem: Sometimes in Paint, moving cursor to left of screen will
cause a very weird phenomenon to occur. An alien rectangular
being makes it's way down the left hand side of screen by
itself! Screen crashes usually, sometimes I get control again.
Fixed By: Tested by MJB
Date: 8/14/91
Fixed after version:
Fix: Do not know, but it doesn't happen now.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 8/2/91
Reported By: MJB
Driver: Xseries
Found in Version: alpha
Priority (1,2 or 3): 1
Problem: Paintroller doing wrong colors in scanline again. Red looks rust.
Afterwards icons missing (linfun?)
Fixed By: MJB
Date: 8/15/91
Fixed after version: alpha
Fix: The global current_linpat was not updated when scanlines drawn
with alternating dither.
Modules affected: Scandev.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 8/14/91
Reported By: MJB
Driver: xseries
Found in Version: alpha
Priority (1,2 or 3): 1
Problem: Paint boxes with rounded corners come up wrong colors and/or
with wrong border colors.
Fixed By: MJB
Date: 8/15/91
Fixed after version: alpha
Fix: The global current_linpat was not updated when scanlines drawn
with alternating dither.
Modules affected: Scandev.asm
Software Anomaly Report
Windows 3.0 Driver
Date: July 1, 1991
Reported By: MJB
Driver: X/Series
Found in Version: after 1.00
Priority (1,2 or 3): 1
Problem: Cursor left behind in solitaire sometimes. Probably turned
on by check cursor when it should still be disabled.
Fixed By: Tested by MJB
Date: 8/15/91
Fixed after version: 1
Fix: Do not have a clue but the problem is gone now!!
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 8/16/91
Reported By: MJB
Driver: XSERIES
Found in Version: 1.00 ALPHA
Priority (1,2 or 3): 2
Problem: Cursor not excluded properly during dialog box test in benchmarks.
Fixed By: MJB
Date: 8/16/91
Fixed after version: 1.00 Alpha
Fix: Enabled flag not knocked down soon enough in savescreenbitmap. Ds not
set up for cursor_exclude function.
Modules affected: ssb.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 19-July-91
Reported By: evh
Driver: X/Series
Found in Version: alpha
Priority (1,2 or 3): 1
Problem:
ToolBook crashes. Nop'ing out Output seems to make ToolBook come up
fine.
Fixed By: MJB
Date: 8/20/91
Fixed after version: 1.00 alpha
Fix: Clipping had been removed for output to memory. So, the code
tried to draw outside the bitmap and caused a protect violation in
standard mode. Put clipping back in.
Modules affected: scanlines.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 21 August 1991
Reported By: jim
Driver: X/SERIES
Found in Version: 8/21/91
Priority (1,2 or 3):
Problem: A few of the patches are missing when you try:
Controll Panel, colors, color palette. One also missing in paintbrush.
Fixed By: MJB
Date: 8/21/91
Fixed after version: 1.00 alpha
Fix: Returning wrong status in output for rectangles I couldn't do. So,
the GDI thought a rect was drawn when it wasn't.
Modules affected: opdevice.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 21 August 1991
Reported By: mjb
Driver: X/SERIES
Found in Version: 8/21/91
Priority (1,2 or 3):
Problem: Using the palette in Control Panel, changing the window background
doesn't always work. Dithered patterns especially are wrong.
Fixed By:
Date: 8/22/91
Fixed after version: 1.00 alpha
Fix: No fix: VGA also screwed up.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 21 August 1991
Reported By: jim
Driver: X/SERIES
Found in Version: 8/21/91 10:00
Priority (1,2 or 3):
Problem: My progress bar is gone! Give it back!
In Trueview (in Xfer) the progress bar that normally
extends across the bottom of the file-picking dialog box
is gone!
Fixed By: MJB
Date: 8/21/91
Fixed after version: 1.00 alpha
Fix: Returning wrong status in output for rectangles I couldn't do. So,
the GDI thought a rect was drawn when it wasn't.
Modules affected: opdevice.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 21 August 1991
Reported By: jimc
Driver: X/SERIES
Found in Version: 8/21/91 10:00 version
256 colors, enhanced mode
Priority (1,2 or 3):
Problem: in SDK paint (in r:\sdk) if you choose one color and both
paint and fill with it, you get different shades of the same color.
Does not happen with VGA driver. Especially dark red (un-dithered).
Fixed By: MJB maybe
Date: 8/22/91
Fixed after version: 1.00 alpha
Fix: Not sure but Jim says fixed now.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 22 August 1991
Reported By: Jim C.
Driver: X/SERIES
Found in Version: 22/8/91 10:00
Windows Mode (real, standard, enh): ENH
Priority (1,2 or 3):
Problem: Another color problem. in paintbrush, there are two light blues.
The one just to the right of the purple and above the puke-mustard shold
be light yellow. On the tseng 16 color driver it is dithered yellow and
white (2 colors). On the tseng 256 color driver it is a off-white that
is very close to normal white. Probably a bug in the tseng 256 color
driver.
Fixed By: ??
Date: 8/23/91
Fixed after version: 1.00 alpha
Fix: Jim says is fixed. Probably some of Eric's color fixes.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 21-Aug-91
Reported By: mjb
Driver: X/Series
Found in Version: alpha
Priority (1,2 or 3): 1
Problem:
In Standard mode, ToolBook will come up fine the first time but not
subsequent times. After this happens, cblts don't work correctly in
winbench either.
Fixed By: MJB
Date: 8/21/91
Fix: Separated out some functionality from vmbufon and vmbufoff in C lib.
We think this is what fixed it.
Modules affected: vmxframe.
Software Anomaly Report
Windows 3.0 Driver
Date: 31-July-91
Reported By: evh
Driver: X/Series 16 color
Found in Version: 1.00 alpha
Priority (1,2 or 3): 3
Problem:
When the color palette is drawn in CorelDraw, sometimes the top
scanline is missing.
Fixed By: MJB
Date: 8/27/91
Fixed after version: 1.00 alpha
Fix: Before doing blkmov of palette to scroll it, replaced cursor_exclude
with cursor_disable. The cursor is unconditionally turned off. Not
clear why the cursor caused a problem with the blkmov.
Modules affected: special.blt, bitblt.asm (external decl).
Software Anomaly Report
Windows 3.0 Driver
Date: 8/23/91
Reported By: jim
Driver: X/SERIES
Found in Version: 8/22/91 2:00 PM
Windows Mode (real, standard, enh): enh
Priority (1,2 or 3):
Problem:
in Corel Draw, when you look at the right end of the palette at the
bottom of the screen, the top line of each swatch is a different color. This
could be the same as the missing scanline in wingif and trueview.
Fixed By: MJB
Date: 8/26/91
Fixed after version: 1.00 alpha
Fix: Changing the cursor_exclude call to cursor_disable in special_blit.
Now I unconditionally turn off the cursor before doing the block move.
For some reason, this fixed the problem.
Modules affected: special.blt, bitblt.asm
Note : this is same fix/bug as sco0112.txt
Software Anomaly Report
Windows 3.0 Driver
Date: 28-Aug-91
Reported By: evh
Driver: X/Series 16 color
Found in Version: 1.00 alpha
Priority (1,2 or 3): 3
Problem:
Color erase does not work.
Fixed By: evh
Date: 28-Aug-91
Fixed after version: 1.00 alpha
Fix:
On reads from the board, colors above 7 did not have the high order
nibble set to Fh. Since all of our color conversion routines return
this nibble as Fh, the rops did not work correctly.
Modules affected:
cblt88.blt
genconst.blt
Software Anomaly Report
Windows 3.0 Driver
Date: 28-Aug-91
Reported By: evh
Driver: X/Series 16 color
Found in Version: 1.00 alpha
Priority (1,2 or 3): 3
Problem:
When returning from the DOS box, the color palette gets screwed up.
Fixed By: evh
Date: 28-Aug-91
Fixed after version: 1.00 alpha
Fix:
When returning from the DOS box, the palette is only reset if palette
management is enabled.
Modules affected:
3xswitch.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 13-Aug-91
Reported By: evh
Driver: X/Series 16 color
Found in Version: 1.00 alpha
Priority (1,2 or 3): 2
Problem:
In Word, the buttons come up red instead of gray.
Fixed By: evh
Date: 28-Aug-91
Fixed after version: 1.00 alpha
Fix:
Paint calls EnumObj at start-up time to enumerate all pens. EnumObj
was never updated for 16 color boards, and was using the middle four
palette entries of the 20 system colors inadvertantly. Since these
colors are all zeroed out on 16 color boards, this was screwing up
the palette. EnumObj now skips these middle four entries.
Modules affected:
EnumObj.asm
n
Software Anomaly Report
Windows 3.0 Driver
Date: 28-Aug-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 2
Problem:
There appears to be a text coordinate problem. To reproduce it,
invoke TourBook. Select 'map', and then select 'What Can ToolBook
Do?.' The window that appears will have text on the left hand side
which does not display properly. The secodn part of the message
appears too high.
Fixed By: PUNT
Date: 8/28/91
Fixed after version:
Fix: VGA FONTS OK. Bug only occurs with 8514 fonts. We have decided
it is a bug in toolbook.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 8/28/91
Reported By: Paul Angstman
Driver: Yours
Found in Version: on the net
Windows Mode (real, standard, enh): Yes
Priority (1,2 or 3): 1
Problem: Open a chapter, reduce the size. If you are still alive, use the
page down key. A real hard crash.
Fixed By: evh
Date: 30-Aug-91
Fixed after version: 1.00 alpha
Fix:
Zero width characters were not being handled properly. In the old
font loading system, zero width characters were simply skipped. This
doesn't work with the new font loading stuff, where we tell PGL how
many characters are being downloaded. Skipping characters gets PGL
out of synch, and it crashes.
Modules affected:
SBFontLoad.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 8/29/91
Reported By: TomM
Driver: X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 1
Problem: Select style from top bar, select define, select ZAPFDINGBATS 18.
CRASH.
Fixed By: evh
Date: 30-Aug-91
Fixed after version: 1.00 alpha
Fix:
This does not appear to be a driver bug. In my Windows setup, I
happen to have a Dingbats font from Bitstream, and everything works
fine. Apparently the VGA Dingbats font that comes with Windows will
not work with drivers like ours which use 8514 font metrics. Also,
it appears that PowerPoint does not properly handle the case where
the font is missing. I will write a technote on this for support.
Modules affected:
None.
Software Anomaly Report
Windows 3.0 Driver
Date: 28-Aug-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 2
Problem:
One of the disks that is prompted for in Setup does not dislpay the
name of the disk.
Fixed By: evh
Date: 28-Aug-91
Fixed after version: 1.00 alpha
Fix:
The wrong disk number was in the oemsetup file.
Modules affected:
oemsetup.525
Software Anomaly Report
Windows 3.0 Driver
Date: 8/29/91
Reported By: TomM
Driver: X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 2
Problem: When running slide show, previous slide is not completely erased.
2 edges are left.
Fixed By: MJB
Date: 8/30/91
Fixed after version: 1.00 alpha
Fix: Rectangles with a NOP pen were not including outline of rect -
NOP pen should be treated like null pointer to pen.
Modules affected: rect_dev.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 30-Aug-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 2
Problem:
Use the zoom utility. Get the little zoom rectangle and drag it
along the bottom of the screen. It will leave residual crap on the
screen.
Fixed By: MJB
Date: 9/1/91
Fixed after version: 2.00 alpha
Fix: If I don't allow y coord of cursor to be greater than yres -1,
this bug doesn't happen. So I added the check.
Modules affected: cursors.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 4-Apr-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 3
Problem:
When you switch to Codeview, the Windows cursor is still active. You
can move the cursor in Codeview and it still moves in Windows. When
you return to Windowws the cursor acts like button 1 is being held down
perpetually. You can reproduce this as follows:
1) Invoke Codeview
2) Run an app
3) Once the app is loaded set a breakpoint in Codeview
4) Run the app until you hit the breakpoint
5) Use the mouse in Codeview to pull down a menu. You
will see the Windows cursor still active.
6) Switch back to Windows and move the cursor over the menu
bar. Without pushing the mouse button, menus will
be pulled down. Pushing the mouse button once ends
this behavior.
What is probably happening is that the mouse isn't being disabled,
and the last mouse down event is being process by Windows instead of
Codeview.
Later:
I noticed that the VGA driver actually removes the cursor from the
screen while in Codeview, and then puts it back up when you switch
back to Windows.
Fixed By: MJB
Date: 9/3/91
Fixed after version: 1.00 alpha
Fix: In Setcursor the cur_flags global wasn't being set to off when
the cursor was turned off without being redefined. Also, setcursor
wasn't turning off the cursor if the lpcursor was null, only before
vmcsrdef was vmcsroff called. Also, in Movecursor, this flag wasn't
being checked. If off, it shouldn't be moved of course.
Modules affected: cursors.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 8/29/91
Reported By: TomM
Driver: X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 1
Problem: Hang during slide show. Possibly 2 problems. On a 4-bit device,
protected violation occurs. 8 bit - fonts?
Fixed By: evh
Date: 5-Sep-91
Fixed after version: 1.00 alpha
Fix:
Not really sure. I put some conditional code in getrle for 4 bit boards,
but I can't confirm that this fixed it.
Modules affected:
getrle.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 30-Aug-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 3
Problem:
It looks like there is a cursor exclude problem. To duplicate this
bug, go into Word and open the file 'keycaps.doc.' As the file is
being displayed, move the cursor over the area in the document where
the graphics will be displayed. When the graphics are then drawn,
the area under the cursor will be end up blank.
Fixed By: evh
Date: 5-Sep-91
Fixed after version: 1.00 alpha
Fix:
Couldn't reproduce.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 30-Aug-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00 alpha
Priority (1,2 or 3): 2
Problem:
We are off by a scanline. To reproduce this bug, click on an icon
which is at the bottom of a window and is partially hidden by the
window bottom. Select 'Properties' from the 'File' menu. Change the
properties (you can just enter a space at the end of the file name
and then delete it), and click 'OK.' When the icon is redrawn, it
will overwrite the a portion of the window bottom.
Fixed By: evh
Date: 5-Sep-91
Fixed after version: 1.00 alpha
Fix:
Could not reproduce.
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 8/28/91
Reported By: Paul Angstman
Driver: Yours
Found in Version: on the net
Windows Mode (real, standard, enh): Yes
Priority (1,2 or 3): 3
Problem: The rounded graphics in Ventura (ellipse, rounded rectangle) are
not drawn solid.
Fixed By: MJB and Chris. PGL windows pline was drawing the last pixel.
The primitives were drawn in xor mode and the last pixel and first
pixel of next line resulted in nop pixel. Chris fixed PGL.
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 28-Aug-91
Reported By: evh
Driver: X/Series 16 color
Found in Version: 1.00 alpha
Priority (1,2 or 3): 3
Problem:
The paint roller (fill) does not work reliably.
Fixed By: MJB
Date: 9/6/91
Fixed after version: 1.00 alpha
Fix: Added check in colorinfo for 16 color device. If 16 colors, indexes
over 7 must be adjusted to last 8 colors in table.
Modules affected: colorinf.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 9/3/91
Reported By: Paul Angstman
Driver: Yours
Found in Version: on the net
Windows Mode (real, standard, enh): Yes
Priority (1,2 or 3): 30033
Problem: Bring up Ventura; open book2.chp (the 2nd one down); change the
view to enlarged view. You will notice the text will be missing in the
part that is supposed to read "Chapter 1". If you change the text size
of that particular line from 36 to 32 you will see wrong characters in
the text string.
Fixed By: evh
Date: 9-Sep-91
Fixed after version: 1.00 alpha
Fix:
There were several problems:
1) PGL was not trapping for an error when it ran out of memory trying
to load a font
2) The driver was not testing for the error, and using the bitmap interface
when the font load failed
Modules affected:
strblt.asm
SBDevice.asm
SBStrDraw.asm
SBFontGet.asm
SBFontLoad.asm
Software Anomaly Report
Windows 3.0 Driver
Date: 9/5/91
Reported By: Richard
Driver: X/Series, 16 color
Found in Version: 1.00 Alpha
Priority (1,2 or 3): 1
Problem: Powerpoint will crash in the "Define styles..." dialog box
when selecting an item from the "colors" combo box control. Failure
may require alternatively (1) selecting a style from the "styles" list
box and (2) selecting a color from "colors".
Fixed By: evh
Date: 9-Sep-91
Fixed after version: 1.00 alpha
Fix:
The conversion table 'rows_and_masks' which is used in the function 'dither'
was not being assembled because the makefile did not define the constant
'HIRES'.
Modules affected:
vmi.mak
REPORTED BUGS
Software Anomaly Report
Windows 3.0 Driver
Date:April 18
Reported By: Dotti
Driver: Cobra
Found in Version:All
Priority (1,2 or 3): 2
Problem:
Text gets "caught" in Toolbox of PageMaker 4.0 when doing flip
screens.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 10-April-91
Reported By: JLK
Driver: Cobra
Found in Version: 0.92
Priority (1,2 or 3): 3
Problem:
This morning I tried running the Elite at 800x600 res and everything
came up smoothly.
The only issue I have encountered is with the size of the window bars
and the type used there. Both the bars and the type are larger than
those used in 800x600 VGA.
(This is a general problem with the driver. The screen metrics are
all set up for 1024 x 768. It runs ok, but it doesn't always look
very good. We may need a separate 600 x 800 driver, or we need to
change Enable to return the correct metrics in the GDIINFO structure
when running at 600 x 800. This needs some exploration. To some
extent it depends on how many people out there really need/use 600 x
800.- evh)
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 5/07/91
Reported By: MJB
Driver: Cobra
Found in Version: .95
Priority (1,2 or 3): 3
Problem: Paintbrush in black and white mode. If you fill screen with a
mostly black pattern (scanlines with a brush), then try to fill
with black, it takes forever.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 11-June-91
Reported By: evh
Driver: X/Series
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem:
The new cmd_wait in vm_tips2.asm doesn't work reliably. Could be a
PGL problem.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 13-June-91
Reported By: Steve Brown, Intel, (fax) 503-693-1924
Driver: Cobra Plus
Found in Version: 1.00
Priority (1,2 or 3): 3
Problem:
The Hewlett-Packard/Agfa Compugraphic Intellifont font driver
displays text under the icons in the Program Manager and displayed at
the bottom of the screen is too large.
Also, when running Lotus Ami Pro 1.2, italicized and bold fonts are
not displayed properly. Spaces sometimes display as tabs.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 13-June-91
Reported By: Steve Brown, Intel, (fax) 503-693-1924
Driver: Cobra Plus
Found in Version: 1.00
Priority (1,2 or 3): 3
Problem:
Special graphics in Lotus Ami Pro do not display properly. One is
the up/down arrow used in some menus.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 13-June-91
Reported By: Steve Brown, Intel, (fax) 503-693-1924
Driver: Cobra Plus
Found in Version: 1.00
Priority (1,2 or 3): 2
Problem:
The slide sorter under the view menu dows not display the
miniaturized slides correctly. They aren't displayed at all.
(Probably DIB's... evh)
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 13-June-91
Reported By: Steve Brown, Intel, (fax) 503-693-1924
Driver: Cobra Plus
Found in Version: 1.00
Priority (1,2 or 3): 1
Problem:
Printing graphics frames from within Lotus Ami Pro generates a UAE.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 19-July-91
Reported By: evh
Driver: X/Series
Found in Version: alpha
Priority (1,2 or 3): 2
Problem:
The application Winfract doesn't work because DIBScreenBlt was never
implemented.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 8/14/91
Reported By: MJB
Driver: XSERIES
Found in Version: ALPHA
Priority (1,2 or 3): 2
Problem: Cursor leaves horiz lines up in title bar while moving it up
there during benchmark of grey text.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 21 August 1991
Reported By: Jim
Driver: X/SERIES
Found in Version: 8/21/91 10:00
Priority (1,2 or 3):
Problem: When minimizing some applications, the horizontal dashed lines
show up. Esp. Wingif and Neko.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 22 August 1991
Reported By: jim
Driver: X/SERIES and ELITE
Found in Version: 8/22/91 10:00
Windows Mode (real, standard, enh): ENH
Priority (1,2 or 3): 2
Problem: In Trueview, during vertical pans, some stray scanlines appear.
To Recreate: load an image, resize to about half size, and drag the
vertical thumb around like a madman (madwoman). I cannot reproduce it
in VGA.
When the vertical thumb is moved, I do a ScrollWindow to move
the image that is there, then invalidate the part of the client area that
is not correct and blt the whole image. Because of clipping, only the
incorrect area is written to.
P.S. This also happens in wingif.
NOTE BY MJB: Cblt puts up the image. vertical pan does special_blit
(vmblkmov) to scroll, Cblt fills in new area. When I checked it
out, special_blit looked ok. I don't have a clue about cblt right
now. Wingif has same disease but diff symptoms -very interesting,
check it out.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 8/23/91
Reported By: jim
Driver: X/SERIES 8/bit
Found in Version: 8/22/91 10:00
Windows Mode (real, standard, enh): ENH
Priority (1,2 or 3):
Problem: There is a long delay in a program called colors2. The program was
written by petzold and demonstrates rgb with scrollbars. When the scrollbars
get moved, the client area of the main screen is updated, there is about a 20
second delay before it is.
Colors2.exe is available in n:\software\xfer
This might be slowing down the toolbook opening.
Note: This is ok on a 4-bit board. The calls to special rect color
the screen. Probably palette mgmt is slowing it down.
Later: Now it is ok on 8-bit. A random occurrance???
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 8/23/91
Reported By: jim
Driver: X/SERIES
Found in Version: 8/22/91 10:00
Windows Mode (real, standard, enh): ENH
Priority (1,2 or 3):
Problem: The area fills in paintbrush are unuseably slow. I accidently
clicked on the background, and it would have taken 20 minutes to
complete.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 8/26/91
Reported By: MJB
Driver: xseries 16 color
Found in Version: 1.00 alpha
Priority (1,2 or 3): 3
Problem: Paint in black and white mode. drawing lines or non rectangular
objects: The bounding rectangle gets filled in black.
Note: After polytodevice draws the line, a series of scanlines are drawn
to mono memory. mono to mono I think. Then bitblt blits the black
rectangle. Maybe bitblt is mono to device. I am sure this is
related to the paint roller prob.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
Software Anomaly Report
Windows 3.0 Driver
Date: 8/29/91
Reported By: MJB
Driver: X/series 1.00 alpha
Found in Version: 1.00 alpha
Priority (1,2 or 3): 3
Problem: 16 color devices paintbrush erase color: If a color is dithered,
consisting of 2 solid colors, when one of the 2 colors is selected,
erase color erases the pixels of that color, leaving the other. I
believe it shouldn't affect the dithered color at all.
example: create a filled rect of the 10th color from left on top row.
select either the 5th or 6th from left. Try erase color.
Fixed By:
Date:
Fixed after version:
Fix:
Modules affected:
